|
|
|
|
|
|
|
Figure 19.1.
The framework of the Universal Data Access architecture. |
|
|
|
|
|
|
|
|
OLE DB (OLE Database) provides the low-level interface to persistent information across the enterprise. This is facilitated by the fact that ADO interacts seamlessly with OLE DB. Earlier, ODBC was mentioned as the predecessor of UDA. Although true in the long run, in the immediate future you can expect ODBC to be the mechanism of choice when you need to work with older drivers from a development standpoint. |
|
|
|
|
|
|
|
|
UDA, centered on ADO, is closely coupled with Microsoft's other rising star, the Microsoft Distributed InterNet Applications architecture (Windows DNA). The name Windows DNA might look like Windows Open System Architecture (WOSA) from days gone by. DNA is sort of the WOSA of the Internet for Microsoft's Windows platforms. DNA offers powerful features in integrating Windows with the Internet, including services for business rules, your graphical user interface, and, of course, persistence of information. DNA's persistence is driven by UDA. As a developer, you utilize UDA through what Microsoft calls Microsoft Data Access Components (MDACs). MDACs include ADO, OLE DB, RDS, and ODBC. |
|
|
|
|
|
|
|
|
Microsoft designed ADO for several critical reasons, including the following: |
|
|
|
|
|
